Skip to content

Use Keyring's own security notices - #18

Merged
entity merged 1 commit into
mainfrom
refactor/use-keyring-emails
Nov 11, 2026
Merged

entity merged 1 commit into
mainfrom
refactor/use-keyring-emails

Conversation

@entity

@entity entity commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Keyring now sends its security notices itself (entity/keyring#83), so the app's twelve copies and their base class go. One SecurityNotice::toMailUsing() callback in the provider gives them the Maizzle template. The five emails a flow needs stay the app's own classes.

The risk responder goes too: Keyring's own now emails the owner about a sign in after several failures or a long quiet period (entity/keyring#84).

Run against package dcc4dc4: 108 PHP tests, PHPStan, Pint, lint, type checks, build, and the 35 browser tests on PHP's server and on Octane, all passing.

@entity
entity merged commit cd4c2ed into main Nov 11, 2026
@entity
entity deleted the refactor/use-keyring-emails branch November 11, 2026 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant